Method and apparatus for processing communication requests

ABSTRACT

A system that incorporates the subject disclosure may perform, for example, operations including receiving a request from a communication device to initiate a communication session, obtaining a first name authority pointer record that replaces a second name authority pointer record responsive to an undesirable fault level in a voice over long term evolution network, obtaining the second name authority pointer record responsive to determining that there is no fault or a tolerable level of faults in the voice over long term evolution network, and initiating the communication session according to one of the first name authority pointer record or the second name authority pointer record obtained by the system. The first name authority pointer record can include instructions for initiating the communication session utilizing a circuit-switched communication network, and the second name authority pointer record can include instructions for initiating the communication session utilizing the voice over long term evolution network. Other embodiments are disclosed.

FIELD OF THE DISCLOSURE

The subject disclosure relates to a method and apparatus for processingcommunication requests.

BACKGROUND

Services provider continue to upgrade their networks from providingcircuit-switched voice communications to packet-switched voicecommunications. Many service providers have upgraded landline networksto support voice over Internet protocol (VoIP). Similarly, it isexpected service providers of wireless communication systems willupgrade their networks to support voice over long term evolution (VoLTE)communications from current second generation (2G) and third generation(3G) wireless voice communications.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 depicts an illustrative embodiment of a method for processingcommunication requests;

FIG. 2 depicts an illustrative embodiment of a flow diagram forinitiating a Voice over Long Term Evolution (VoLTE) communicationsession when the VoLTE network is not subject to an undesirable faultlevel in accordance with the method of FIG. 1;

FIG. 3 depicts an illustrative embodiment of a flow diagram forinitiating a Public Line Mobile Network (PLMN) for a 2G or a 3Gcommunication session when the VoLTE network is experiencing anundesirable fault level in accordance with the method of FIG. 1;

FIG. 4 depicts illustrative embodiment of a communication system thatoperates according to the method of FIG. 1;

FIG. 5 depicts an illustrative embodiment of a communication device; and

FIG. 6 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions, when executed, maycause the machine to perform any one or more of the methods describedherein.

DETAILED DESCRIPTION

The subject disclosure describes, among other things, illustrativeembodiments for mitigating faults in a VoLTE network. Other embodimentsare included in the subject disclosure.

One embodiment of the subject disclosure includes a method forreceiving, by a system comprising a processor, a request from acommunication device to initiate a communication session, obtaining, bythe system, a first name authority pointer record that replaces a secondname authority pointer record responsive to determining that there is anundesirable fault level in a voice over long term evolution network,obtaining, by the system, the second name authority pointer recordresponsive to determining that there is no fault or a tolerable level offaults in the voice over long term evolution network, and initiating, bythe system, the communication session according to one of the first nameauthority pointer record or the second name authority pointer recordobtained by the system. In this embodiment the first name authoritypointer record can include instructions for initiating the communicationsession utilizing a circuit-switched communication network, and thesecond name authority pointer record can include instructions forinitiating the communication session utilizing the voice over long termevolution network.

One embodiment of the subject disclosure includes a machine-readablestorage medium including executable instructions, which when executed bya processor, cause the processor to perform operations includingreceiving a request from a communication device to initiate acommunication session, obtaining a first name authority pointer recordin lieu of a second name authority pointer record responsive todetermining that there is an undesirable malfunction in apacket-switched network, where the first name authority pointer recordcomprises instructions for initiating the communication sessionutilizing a circuit-switched communication network, obtaining the secondname authority pointer record responsive to determining that there is nomalfunction or a tolerable level of malfunctions in the packet-switchednetwork, where the second name authority pointer record comprisesinstructions for initiating the communication session utilizing thepacket-switched network, and initiating the communication sessionaccording to one of the first name authority pointer record or thesecond name authority pointer record obtained by the processor.

One embodiment of the subject disclosure includes a device including amemory to store executable instructions, and a processor coupled to thememory. Execution of the executable instructions can cause the processorto perform operations including receiving a request from a communicationdevice to initiate a communication session in a packet-switched network,obtaining a first name authority pointer record responsive todetermining that there is an undesirable operational state in thepacket-switched network, wherein the first name authority pointer recordcomprises instructions for initiating the communication sessionutilizing a circuit-switched communication network, obtaining a secondname authority pointer record responsive to determining that there is adesirable operation state in the packet-switched network, wherein thesecond name authority pointer record comprises instructions forinitiating the communication session utilizing the packet-switchednetwork, and initiating the communication session according to one ofthe first name authority pointer record or the second name authoritypointer record obtained by the processor.

FIG. 1 depicts an illustrative embodiment of a method 100 for processingcommunication requests in a communication system that supports bothVoice over Long Term Evolution (VoLTE) communications and Public LineMobile Network (PLMN) or 2/3G wireless communications. In oneembodiment, method 100 can begin with step 102 in which a first databasestoring name authority pointer records (herein referred to as NAPTRrecords) is created to force a VoLTE communication request to result ina PLMN communication session. At step 104 a second database of NAPTRrecords is created, whereby such NAPTR records result in VoLTEcommunication requests being processed as VoLTE communication sessions.

A tElephone NUmber Mapping (ENUM) server can be instructed to use thefirst database when a VoLTE network experiences a communication fault.The extent of the communication fault can be partial (e.g., ametropolitan area, a cluster of routers, an intermittent interruption incommunications by a network node, etc.) or a catastrophic fault (e.g.,network faults across a state or geographic regions). The ENUM servercan be instructed to use the second database when the VoLTE network isnot experiencing faults or if faults are present, the degree or volumeof network elements experiencing a fault is considered tolerable. Afault can represent any undesirable characteristics in a VoLTE networksuch as a malfunctioning network node, excess packet losses at a networknode, a network node that has been compromised by an unauthorized thirdparty, clusters of malfunctioning network nodes, and so on. A networknode can represent a network communication device used for facilitatingend to end communications for end user equipment.

NAPTR records such as the one below can be stored in the first database,which can represent an “outage” ENUM database to force a VoLTEcommunication request to be processed as a PLMN communication session:

$ORIGIN 1.1.1.1.2.2.2.2.1.5.1.e164.arpa.IN NAPTR 100 20 “u” “E2U+pstn:tel” “!̂.*$!tel:+15122221111!”.

The second database, which can represent a “normal operations” ENUMdatabase, can store NAPTR records such as the one below to so that VoLTEcommunication requests are processed as VoLTE communication sessions:

$ORIGIN 1.1.1.1.2.2.2.2.1.5.1.e164.arpa.IN NAPTR 100 20 “u” “E2U+sip”“!̂.*$!sip:+15122221111@one.domain.net;user=phone!”.

Changing the ENUM Service field “E2U+sip” to “E2U+pstn:tel” and therelated protocol “$!sip:” to “$!tel:” can cause a VoLTE communicationrequest to be processed by a network node as a PLMN communicationsession via 2G/3G circuit switch networks instead of 4G/LTE networks.NAPTR records for outage conditions and normal conditions, respectively,can be created in the first and second databases for new subscriberdevices as shown above. A benefit of a dual database approach is that itminimizes time to transition between an normal operating state of theVoLTE network to an outage condition, and vice-versa.

In another embodiment, a single database, can be configured with theENUM Service field “E2U+sip” when VoLTE network conditions have anacceptable level of faults or no faults at all. Under these conditions,the single database operates as an ENUM database operating under“normal” conditions. When fault conditions exceed a desired operatingcondition, the “normal” ENUM database can be reconfigured to replace all“E2U+sip” fields with “E2U+pstn:tel” and “$!sip:” fields with :$!tel:”.Under these conditions, the single database operates as an ENUM databaseoperating under “outage” conditions. When operating conditions return toacceptable levels, the “outage” ENUM database can be reconfigured toreplace all “E2U+pstn:tel” and “$!tel:” fields of previously VoLTE NAPTRrecords with “E2U+sip” and “$!sip:” fields, respectively. In theforegoing embodiment, a NAPTR record can be created for a new subscriberdevice utilizing the “E2U+pstn:tel” and “$!tel:” fields when a VoLTEnetwork outage condition is present, or the “E2U+sip” and “$!sip:” whentheVoLTE network is operating under desirable conditions.

In yet another embodiment, a database can be created at step 106 withNAPTR records that can accomplish similar results as described above. Inone embodiment, a first type of order and precedence fields can be usedfor VoLTE to VoLTE communication sessions, while another type of orderand precedence fields can be used to force VoLTE to PLMN communicationsessions. For example, [100 20] (order/precedence) fields can be usedfor designating VoLTE to VoLTE communication sessions, while [100 30](order/precedence) fields can be used to force VoLTE to PLMNcommunication sessions, such as shown below.

$ORIGIN 1.1.1.1.2.2.2.2.1.5.1.e164.arpa.IN NAPTR 100 20 “u” “E2U+sip”“!̂.*$!sip:+15122221111@one.domain.net;user=phone!”.IN NAPTR 100 30 “u” “E2U+pstn:tel” “!̂.*$!tel:+15122221111!”.

Call Session Control Function (CSCF) servers can receive both of theabove NAPR records from an ENUM server. When an undesirable level ofnetwork faults are present in the VoLTE network, CSCF's can be informedby a central system to use the NAPTR record with the [100 30] fields,and ignore NAPTR records with [100 20] fields. Thus, forcing a VoLTEcommunication request to be processed as a PLMN communication session.When the fault level diminishes to an acceptable level, the CSCF's canbe directed to use the NAPTR records with the [100 20] fields and ignoreNAPTR records with the [100 30] fields. In an alternative embodiment,the ENUM server can be directed by a central system to provide CSCF'swith NAPTR records with the [100 20] fields when VoLTE networkconditions are at an acceptable level, and provide NAPTR records withthe [100 30] fields when a fault level exceeds acceptable norms or aservice provider threshold. A benefit of multiple NAPTR records withorder precedence fields to address outage and normal operatingconditions is that it minimizes time to transition between an normaloperating state of the VoLTE network to an outage condition, andvice-versa.

According to an IETF standard, the lowest combination of(order/precedence) will be executed first, so [100, 20] will be executedfirst in this illustration. If the CSCF is unable to successfully usethis NAPTR record to establish a communication session, then the NAPTRrecord with [100, 30] will be executed. To force a circuit-switchedcommunication session when the VoLTE network is experiencing anundesirable fault, the ENUM server can be directed to comment out thespecific [100 20] NAPTR record by adding a semicolon (;) preceding therecord (e.g., ;IN NAPTR 100 20 . . . ). See example below.

$ORIGIN 1.1.1.1.2.2.2.2.1.5.1.e164.arpa.;IN NAPTR 100 20 “u” “E2U+sip”“!A.*$!sip:+15122221111@one.domain.net;user=phone!”.IN NAPTR 100 30 “u” “E2U+pstn:tel” “!̂.*$!tel:+15122221111!”.

In the foregoing embodiment, NAPTR records can be created with the [10020] and the [100 30] fields for new subscriber devices to accomplishsimilar results as described above.

With these embodiments in mind, the ENUM server can be provisioned atstep 108 according to a dual database of NAPTR records as described insteps 102-104 that are selected by the ENUM server according to a stateof the VoLTE network, a single database of NAPTR records that are editedby each ENUM server in the network or a central system running a scriptto update network ENUM servers according to a state of the VoLTEnetwork, or a combined database of NAPTR records that are selectable bythe ENUM server or CSCF according to the order and precedence fields asdescribed by step 106.

In one embodiment, the foregoing NAPTR record strategies can be appliedonly to communication devices capable of VoLTE communications. For Voiceover Internet Protocol (VoIP) communication requests, NAPTR records canbe kept unchanged regardless of network conditions. Accordingly,independent of the state of a VoLTE network, NAPTR records of VoIPcommunication devices such as shown below, will not be changed in anENUM database.

$ORIGIN 1.1.1.1.2.2.2.2.1.5.1.e164.arpa.IN NAPTR 100 10 “u” “E2U+sip”“!A.*$!sip:+15122221111@one.domain.net;user=phone!”.

Once the ENUM server is provisioned with one or more databases asdescribed above, method 100 can be put into practice for processingcommunication requests initiated by communication devices. Method 100can continue, for example, at step 110 where a CSCF receives acommunication request from a communication device to initiate acommunication session. At step 112, the CSCF can initiate an ENUM querywith an ENUM server to process the communication request. The ENUMserver can determine at step 112 from the query the identity of thecommunication device by way of an E.164 number or SIP URI. The identitycan then be used to determine if the communication is a landline deviceconfigured for VoIP communications or a mobile device configured forVoLTE communications. If the device is determined to be a landlinedevice, then the ENUM server provides to the CSCF at step 114 a NAPTRrecord instructing the CSCF to initiate a VoIP communication sessionindependent of the state the VoLTE network.

If the communication device, however, is a VoLTE-capable communicationdevice, and the request is for initiating a communication session usingthe VoLTE network, then the ENUM server proceeds to step 116 todetermine if the VoLTE network is experiencing a fault that is deemedundesirable. As noted earlier the fault can be a partial or substantialfault. The threshold, and parameters measured by service providerequipment to determine when a fault in the VoLTE network is undesirablecan be defined by the service provider according to the serviceprovider's operational objectives. If there is no fault, or a tolerablelevel of faults, the ENUM server will provide in step 120 a NAPTR record(such as the embodiments previously described) that instructs the CSCFto initiate a communication session utilizing the VoLTE network. If,however, an undesirable fault is detected, the ENUM server can providethe CSCF at step 118 a NAPTR record that instructs the CSCF to use aPLMN network to initiate a circuit-switched communication session.

As noted earlier, in one embodiment the ENUM server can select betweenNAPTR databases to choose a NAPTR record that achieves the objectives ofstep 118 or step 120. Alternatively, the ENUM server can providemultiple NAPTR records to the CSCF and allow it to choose between themaccording to the order and precedence fields and knowledge of thecondition of the VoLTE network, which can be passed to the CSCF by acentral monitoring system operating from an IP Multimedia Subsystem(IMS) network.

Step 120 can be described by the flow diagram of FIG. 2, which depicts aCSCF initiating a VoLTE communication session based on the NAPTR recordprovided by the ENUM server at step 120 when the VoLTE network is notsubject to an undesirable fault. Step 118 can be described by the flowdiagram of FIG. 3, which depicts the CSCF initiating a PLMNcommunication session based on the NAPTR record provided by the ENUMserver at step 118 when the VoLTE network is experiencing an undesirablefault.

FIG. 4 depicts an illustrative embodiment of a communication system 400employing an IMS network architecture to facilitate the combinedservices of circuit-switched and packet-switched systems. The ENUMserver, CSCF servers, HSS and other network nodes of the IMS network 450described below can be configured to operate as described above inrelation to method 100 of FIG. 1.

Communication system 400 can comprise a Home Subscriber Server (HSS)440, an ENUM server 430, and other network elements of an IMS network450. The IMS network 450 can establish communications betweenIMS-compliant communication devices (CDs) 401, 402, PLMN CDs 403, 405,and combinations thereof by way of a Media Gateway Control Function(MGCF) 420 coupled to a PLMN network 460. The MGCF 420 need not be usedwhen a communication session involves IMS CD to IMS CD communications. Acommunication session involving at least one PLMN CD may utilize theMGCF 420.

IMS CDs 401, 402 can register with the IMS network 450 by contacting aProxy CSCF (P-CSCF) which communicates with an interrogating CSCF(I-CSCF), which in turn, communicates with a Serving CSCF (S-CSCF) toregister the CDs with the HSS 440. To initiate a communication sessionbetween CDs, an originating IMS CD 401 can submit a Session InitiationProtocol (SIP INVITE) message to an originating P-CSCF 404 whichcommunicates with a corresponding originating S-CSCF 406. Theoriginating S-CSCF 406 can submit the SIP INVITE message to one or moreapplication servers (ASs) 417 that can provide a variety of services toIMS subscribers.

For example, the application servers 417 can be used to performoriginating call feature treatment functions on the calling party numberreceived by the originating S-CSCF 406 in the SIP INVITE message.Originating treatment functions can include determining whether thecalling party number has international calling services, call IDblocking, calling name blocking, 7-digit dialing, and/or is requestingspecial telephony features (e.g., *72 forward calls, *73 cancel callforwarding, *67 for caller ID blocking, and so on). Based on initialfilter criteria (iFCs) in a subscriber profile associated with a CD, oneor more application servers may be invoked to provide various calloriginating feature services.

Additionally, the originating S-CSCF 406 can submit queries to the ENUMsystem 430 to translate an E.164 telephone number in the SIP INVITEmessage to a SIP Uniform Resource Identifier (URI) if the terminatingcommunication device is IMS-compliant. The SIP URI can be used by anInterrogating CSCF (I-CSCF) 407 to submit a query to the HSS 440 toidentify a terminating S-CSCF 414 associated with a terminating IMS CDsuch as reference 402. Once identified, the I-CSCF 407 can submit theSIP INVITE message to the terminating S-CSCF 414. The terminating S-CSCF414 can then identify a terminating P-CSCF 416 associated with theterminating CD 402. The P-CSCF 416 may then signal the CD 402 toestablish Voice over Internet Protocol (VoIP) communication services,thereby enabling the calling and called parties to engage in voiceand/or data communications. Based on the iFCs in the subscriber profile,one or more application servers may be invoked to provide various callterminating feature services, such as call forwarding, do not disturb,music tones, simultaneous ringing, sequential ringing, etc.

In some instances the aforementioned communication process issymmetrical. Accordingly, the terms “originating” and “terminating” inFIG. 4 may be interchangeable. It is further noted that communicationsystem 400 can be adapted to support video conferencing. In addition,communication system 400 can be adapted to provide the IMS CDs 401, 402with the multimedia and Internet services of communication system 400 ofFIG. 4.

If the terminating communication device is instead a PLMN CD such as CD403 or CD 405 (in instances where the cellular phone only supportscircuit-switched voice communications), the ENUM system 430 can respondwith an unsuccessful address resolution which can cause the originatingS-CSCF 406 to forward the call to the MGCF 420 via a Breakout GatewayControl Function (BGCF) 419. The MGCF 420 can then initiate the call tothe terminating PLMN CD over the PLMN network 460 to enable the callingand called parties to engage in voice and/or data communications.

It is further appreciated that the CDs of FIG. 4 can operate as wirelineor wireless devices. For example, the CDs of FIG. 4 can becommunicatively coupled to a cellular base station 421, a femtocell, aWiFi router, a Digital Enhanced Cordless Telecommunications (DECT) baseunit, or another suitable wireless access unit to establishcommunications with the IMS network 450 of FIG. 4. The cellular accessbase station 421 can operate according to common wireless accessprotocols such as GSM, CDMA, TDMA, UMTS, WiMax, SDR, LTE, and so on.Other present and next generation wireless network technologies can beused by one or more embodiments of the subject disclosure. Accordingly,multiple wireline and wireless communication technologies can be used bythe CDs of FIG. 4.

Cellular phones supporting LTE can support packet-switched voice andpacket-switched data communications and thus may operate asIMS-compliant mobile devices. In this embodiment, the cellular basestation 421 may communicate directly with the IMS network 450 as shownby the arrow connecting the cellular base station 421 and the P-CSCF416.

Alternative forms of a CSCF can operate in a device, system, component,or other form of centralized or distributed hardware and/or software.Indeed, a respective CSCF may be embodied as a respective CSCF systemhaving one or more computers or servers, either centralized ordistributed, where each computer or server may be configured to performor provide, in whole or in part, any method, step, or functionalitydescribed herein in accordance with a respective CSCF. Likewise, otherfunctions, servers and computers described herein, including but notlimited to, the HSS, the ENUM server, the BGCF, and the MGCF, can beembodied in a respective system having one or more computers or servers,either centralized or distributed, where each computer or server may beconfigured to perform or provide, in whole or in part, any method, step,or functionality described herein in accordance with a respectivefunction, server, or computer.

For illustration purposes only, the terms S-CSCF, P-CSCF, I-CSCF, and soon, can be server devices, but may be referred to in the subjectdisclosure without the word “server.” It is also understood that anyform of a CSCF server can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as DIAMETER commandsare terms can include features, methodologies, and/or fields that may bedescribed in whole or in part by standards bodies such as 3^(rd)Generation Partnership Project (3GPP). It is further noted that some orall embodiments of the subject disclosure may in whole or in partmodify, supplement, or otherwise supersede final or proposed standardspublished and promulgated by 3GPP.

FIG. 5 depicts an illustrative embodiment of a communication device 500.Communication device 500 can serve in whole or in part as anillustrative embodiment of the devices depicted in FIG. 4. Thecommunication device 500 described below can embodiment any devicedescribed above, and when applicable can be configured in whole or inpart to operate as described above in relation to method 100 of FIG. 1.

With this in mind, communication device 500 can comprise a wirelineand/or wireless transceiver 502 (herein transceiver 502), a userinterface (UI) 504, a power supply 514, a location receiver 516, amotion sensor 518, an orientation sensor 520, and a controller 506 formanaging operations thereof. The transceiver 502 can support short-rangeor long-range wireless access technologies such as Bluetooth, ZigBee,WiFi, DECT, or cellular communication technologies, just to mention afew. Cellular technologies can include, for example, CDMA-1X,UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO, WiMAX, SDR, LTE, as well asother next generation wireless communication technologies as they arise.The transceiver 502 can also be adapted to support circuit-switchedwireline access technologies (such as PLMN), packet-switched wirelineaccess technologies (such as TCP/IP, VoIP, etc.), and combinationsthereof.

The UI 504 can include a depressible or touch-sensitive keypad 508 witha navigation mechanism such as a roller ball, a joystick, a mouse, or anavigation disk for manipulating operations of the communication device500. The keypad 508 can be an integral part of a housing assembly of thecommunication device 500 or an independent device operably coupledthereto by a tethered wireline interface (such as a USB cable) or awireless interface supporting for example Bluetooth. The keypad 508 canrepresent a numeric keypad commonly used by phones, and/or a QWERTYkeypad with alphanumeric keys. The UI 504 can further include a display510 such as monochrome or color LCD (Liquid Crystal Display), OLED(Organic Light Emitting Diode) or other suitable display technology forconveying images to an end user of the communication device 500. In anembodiment where the display 510 is touch-sensitive, a portion or all ofthe keypad 508 can be presented by way of the display 510 withnavigation features.

The display 510 can use touch screen technology to also serve as a userinterface for detecting user input. As a touch screen display, thecommunication device 500 can be adapted to present a user interface withgraphical user interface (GUI) elements that can be selected by a userwith a touch of a finger. The touch screen display 510 can be equippedwith capacitive, resistive or other forms of sensing technology todetect how much surface area of a user's finger has been placed on aportion of the touch screen display. This sensing information can beused to control the manipulation of the GUI elements or other functionsof the user interface. The display 510 can be an integral part of thehousing assembly of the communication device 500 or an independentdevice communicatively coupled thereto by a tethered wireline interface(such as a cable) or a wireless interface.

The UI 504 can also include an audio system 512 that utilizes audiotechnology for conveying low volume audio (such as audio heard inproximity of a human ear) and high volume audio (such as speakerphonefor hands free operation). The audio system 512 can further include amicrophone for receiving audible signals of an end user. The audiosystem 512 can also be used for voice recognition applications. The UI504 can further include an image sensor 513 such as a charged coupleddevice (CCD) camera for capturing still or moving images.

The power supply 514 can utilize common power management technologiessuch as replaceable and rechargeable batteries, supply regulationtechnologies, and/or charging system technologies for supplying energyto the components of the communication device 500 to facilitatelong-range or short-range portable applications. Alternatively, or incombination, the charging system can utilize external power sources suchas DC power supplied over a physical interface such as a USB port orother suitable tethering technologies.

The location receiver 516 can utilize location technology such as aglobal positioning system (GPS) receiver capable of assisted GPS foridentifying a location of the communication device 500 based on signalsgenerated by a constellation of GPS satellites, which can be used forfacilitating location services such as navigation. The motion sensor 518can utilize motion sensing technology such as an accelerometer, agyroscope, or other suitable motion sensing technology to detect motionof the communication device 500 in three-dimensional space. Theorientation sensor 520 can utilize orientation sensing technology suchas a magnetometer to detect the orientation of the communication device500 (north, south, west, and east, as well as combined orientations indegrees, minutes, or other suitable orientation metrics).

The communication device 500 can use the transceiver 502 to alsodetermine a proximity to a cellular, WiFi, Bluetooth, or other wirelessaccess points by sensing techniques such as utilizing a received signalstrength indicator (RSSI) and/or signal time of arrival (TOA) or time offlight (TOF) measurements. The controller 506 can utilize computingtechnologies such as a microprocessor, a digital signal processor (DSP),programmable gate arrays, application specific integrated circuits,and/or a video processor with associated storage memory such as Flash,ROM, RAM, SRAM, DRAM or other storage technologies for executingcomputer instructions, controlling, and processing data supplied by theaforementioned components of the communication device 400.

Other components not shown in FIG. 5 can be used in one or moreembodiments of the subject disclosure. For instance, the communicationdevice 500 can include a reset button (not shown). The reset button canbe used to reset the controller 506 of the communication device 500. Inyet another embodiment, the communication device 500 can also include afactory default setting button positioned, for example, below a smallhole in a housing assembly of the communication device 500 to force thecommunication device 500 to re-establish factory settings. In thisembodiment, a user can use a protruding object such as a pen or paperclip tip to reach into the hole and depress the default setting button.The communication device 400 can also include a slot for adding orremoving an identity module such as a Subscriber Identity Module (SIM)card. SIM cards can be used for identifying subscriber services,executing programs, storing subscriber data, and so forth.

The communication device 500 as described herein can operate with moreor less of the circuit components shown in FIG. 5. These variantembodiments can be used in one or more embodiments of the subjectdisclosure.

It should be understood that devices described in the exemplaryembodiments can be in communication with each other via various wirelessand/or wired methodologies. The methodologies can be links that aredescribed as coupled, connected and so forth, which can includeunidirectional and/or bidirectional communication over wireless pathsand/or wired paths that utilize one or more of various protocols ormethodologies, where the coupling and/or connection can be direct (e.g.,no intervening processing device) and/or indirect (e.g., an intermediaryprocessing device such as a router).

FIG. 6 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 600 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. In some embodiments, the machine may beconnected (e.g., using a network 626) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient user machine in server-client user network environment, or as apeer machine in a peer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet PC, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

The computer system 600 may include a processor (or controller) 602(e.g., a central processing unit (CPU), a graphics processing unit (GPU,or both), a main memory 604 and a static memory 606, which communicatewith each other via a bus 608. The computer system 600 may furtherinclude a display unit 610 (e.g., a liquid crystal display (LCD), a flatpanel, or a solid state display. The computer system 600 may include aninput device 612 (e.g., a keyboard), a cursor control device 614 (e.g.,a mouse), a disk drive unit 616, a signal generation device 618 (e.g., aspeaker or remote control) and a network interface device 620. Indistributed environments, the embodiments described in the subjectdisclosure can be adapted to utilize multiple display units 610controlled by two or more computer systems 600. In this configuration,presentations described by the subject disclosure may in part be shownin a first of the display units 610, while the remaining portion ispresented in a second of the display units 610.

The disk drive unit 616 may include a tangible computer-readable storagemedium 622 on which is stored one or more sets of instructions (e.g.,software 624) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above. Theinstructions 624 may also reside, completely or at least partially,within the main memory 604, the static memory 606, and/or within theprocessor 602 during execution thereof by the computer system 600. Themain memory 604 and the processor 602 also may constitute tangiblecomputer-readable storage media.

Dedicated hardware implementations including, but not limited to,application specific integrated circuits, programmable logic arrays andother hardware devices that can likewise be constructed to implement themethods described herein. Application specific integrated circuits andprogrammable logic array can use downloadable instructions for executingstate machines and/or circuit configurations to implement embodiments ofthe subject disclosure. Applications that may include the apparatus andsystems of various embodiments broadly include a variety of electronicand computer systems. Some embodiments implement functions in two ormore specific interconnected hardware modules or devices with relatedcontrol and data signals communicated between and through the modules,or as portions of an application-specific integrated circuit. Thus, theexample system is applicable to software, firmware, and hardwareimplementations.

In accordance with various embodiments of the subject disclosure, theoperations or methods described herein are intended for operation assoftware programs or instructions running on or executed by a computerprocessor or other computing device, and which may include other formsof instructions manifested as a state machine implemented with logiccomponents in an application specific integrated circuit or fieldprogrammable gate array. Furthermore, software implementations (e.g.,software programs, instructions, etc.) including, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the methods described herein. It is furthernoted that a computing device such as a processor, a controller, a statemachine or other suitable device for executing instructions to performoperations or methods may perform such operations directly or indirectlyby way of one or more intermediate devices directed by the computingdevice.

While the tangible computer-readable storage medium 622 is shown in anexample embodiment to be a single medium, the term “tangiblecomputer-readable storage medium” should be taken to include a singlemedium or multiple media (e.g., a centralized or distributed database,and/or associated caches and servers) that store the one or more sets ofinstructions. The term “tangible computer-readable storage medium” shallalso be taken to include any non-transitory medium that is capable ofstoring or encoding a set of instructions for execution by the machineand that cause the machine to perform any one or more of the methods ofthe subject disclosure. The term “non-transitory” as in a non-transitorycomputer-readable storage includes without limitation memories, drives,devices and anything tangible but not a signal per se.

The term “tangible computer-readable storage medium” shall accordinglybe taken to include, but not be limited to: solid-state memories such asa memory card or other package that houses one or more read-only(non-volatile) memories, random access memories, or other re-writable(volatile) memories, a magneto-optical or optical medium such as a diskor tape, or other tangible media which can be used to store information.Accordingly, the disclosure is considered to include any one or more ofa tangible computer-readable storage medium, as listed herein andincluding art-recognized equivalents and successor media, in which thesoftware implementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the disclosure is not limited to such standards andprotocols. Each of the standards for Internet and other packet switchednetwork transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) representexamples of the state of the art. Such standards are from time-to-timesuperseded by faster or more efficient equivalents having essentiallythe same functions. Wireless standards for device detection (e.g.,RFID), short-range communications (e.g., Bluetooth, WiFi, Zigbee), andlong-range communications (e.g., WiMAX, GSM, CDMA, LTE) can be used bycomputer system 600.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Theexemplary embodiments can include combinations of features and/or stepsfrom multiple embodiments. Other embodiments may be utilized and derivedtherefrom, such that structural and logical substitutions and changesmay be made without departing from the scope of this disclosure. Figuresare also merely representational and may not be drawn to scale. Certainproportions thereof may be exaggerated, while others may be minimized.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any arrangement calculated toachieve the same purpose may be substituted for the specific embodimentsshown. This disclosure is intended to cover any and all adaptations orvariations of various embodiments. Combinations of the aboveembodiments, and other embodiments not specifically described herein,can be used in the subject disclosure.

The Abstract of the Disclosure is provided with the understanding thatit will not be used to interpret or limit the scope or meaning of theclaims. In addition, in the foregoing Detailed Description, it can beseen that various features are grouped together in a single embodimentfor the purpose of streamlining the disclosure. This method ofdisclosure is not to be interpreted as reflecting an intention that theclaimed embodiments require more features than are expressly recited ineach claim. Rather, as the following claims reflect, inventive subjectmatter lies in less than all features of a single disclosed embodiment.Thus the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separately claimedsubject matter.

What is claimed is:
 1. A method, comprising: receiving, by a systemcomprising a processor, a request from a communication device toinitiate a communication session; obtaining, by the system, a first nameauthority pointer record that replaces a second name authority pointerrecord responsive to determining that there is an undesirable faultlevel in a voice over long term evolution network, wherein the firstname authority pointer record comprises instructions for initiating thecommunication session utilizing a circuit-switched communicationnetwork, and wherein the second name authority pointer record comprisesinstructions for initiating the communication session utilizing thevoice over long term evolution network; obtaining, by the system, thesecond name authority pointer record responsive to determining thatthere is no fault or a tolerable level of faults in the voice over longterm evolution network; and initiating, by the system, the communicationsession according to one of the first name authority pointer record orthe second name authority pointer record obtained by the system.
 2. Themethod of claim 1, further comprising determining whether thecommunication device is configured for voice over internet protocolcommunications or configured for voice over long term evolutioncommunications, wherein obtaining the first name authority pointerrecord is further responsive to determining that the communicationdevice is configured for voice over long term evolution communications.3. The method of claim 2, further comprising obtaining a third nameauthority pointer record comprising instructions for initiating thecommunication session utilizing a voice over internet protocolresponsive to determining that the communication device is configuredfor voice over internet protocol communications regardless of whetherthere is the undesirable fault level in the voice over long termevolution network.
 4. The method of claim 1, wherein the systemcomprises a call session control function device.
 5. The method of claim1, wherein the instructions of the first name authority pointer recordcomprise a field that directs the system to utilize a circuit-switchednetwork for initiating the communication session.
 6. The method of claim1, wherein the instructions of the second name authority pointer recordcomprise a field that directs the system to utilize the voice over longterm evolution network for initiating the communication session.
 7. Themethod of claim 1, wherein the first name authority pointer record isstored in a first database, and wherein the second name authoritypointer record is stored in a second database.
 8. The method of claim 7,further comprising: utilizing, by the system, the first database toprocess requests from communication devices when there is theundesirable fault level in the voice over long term evolution network;and utilizing, by the system, the second database to process therequests from the communication devices when there is no fault or thetolerable level of faults in the voice over long term evolution network.9. The method of claim 1, wherein the instructions of the first nameauthority pointer record comprise order and precedence fields thatdirect the system to utilize a circuit-switched network for initiatingthe communication session.
 10. The method of claim 1, wherein theinstructions of the second name authority pointer record comprise orderand precedence fields that direct the system to utilize the voice overlong term evolution network for initiating the communication session.11. The method of claim 1, wherein the undesirable fault level in thevoice over long term evolution network comprises a malfunction in anetwork element of the voice over long term evolution network, whereinthe communication device comprises a mobile communication device.
 12. Amachine-readable storage medium comprising executable instructions,which when executed by a processor, cause the processor to performoperations comprising: receiving a request from a communication deviceto initiate a communication session; obtaining a first name authoritypointer record in lieu of a second name authority pointer recordresponsive to determining that there is an undesirable malfunction in apacket-switched network, wherein the first name authority pointer recordcomprises instructions for initiating the communication sessionutilizing a circuit-switched communication network; obtaining the secondname authority pointer record responsive to determining that there is nomalfunction or a tolerable level of malfunctions in the packet-switchednetwork, wherein the second name authority pointer record comprisesinstructions for initiating the communication session utilizing thepacket-switched network; and initiating the communication sessionaccording to one of the first name authority pointer record or thesecond name authority pointer record obtained by the processor.
 13. Themachine-readable storage medium of claim 12, wherein the operationsfurther comprise storing the first name authority pointer record in afirst database and storing the second name authority pointer record in asecond database.
 14. The machine-readable storage medium of claim 13,wherein the operations further comprise: utilizing the first databasewhen the packet-switched network has the undesirable malfunction; andutilizing the second database when the packet-switched network has nomalfunction or the tolerable level of malfunctions.
 15. Themachine-readable storage medium of claim 12, wherein the packet-switchednetwork comprises a voice over long term evolution network.
 16. Themachine-readable storage medium of claim 12, wherein the undesirablemalfunction in the packet-switched network comprises a malfunction in anetwork element of the packet-switched network.
 17. The machine-readablestorage medium of claim 12, wherein the communication device comprises aportable communication device.
 18. A device, comprising: a memory tostore executable instructions; and a processor coupled to the memory,wherein execution of the executable instructions causes the processor toperform operations comprising: receiving a request from a communicationdevice to initiate a communication session in a packet-switched network;obtaining a first name authority pointer record responsive todetermining that there is an undesirable operational state in thepacket-switched network, wherein the first name authority pointer recordcomprises instructions for initiating the communication sessionutilizing a circuit-switched communication network; obtaining a secondname authority pointer record responsive to determining that there is adesirable operation state in the packet-switched network, wherein thesecond name authority pointer record comprises instructions forinitiating the communication session utilizing the packet-switchednetwork; and initiating the communication session according to one ofthe first name authority pointer record or the second name authoritypointer record obtained by the processor.
 19. The device of claim 18,wherein the operations further comprise storing the first name authoritypointer record in a first database and storing the second name authoritypointer record in a second database.
 20. The device of claim 19, whereinthe operations further comprise: utilizing the first database when thepacket-switched network has the undesirable operational state; andutilizing the second database when the packet-switched network has thedesirable operation state.